home *** CD-ROM | disk | FTP | other *** search
- Path: scoop.eco.twg.com!usenet
- From: mike@vishnu.eco.twg.com (This space intentionally left blank)
- Newsgroups: comp.lang.c++,rec.games.programmer,alt.msdos.programmer,comp.programming
- Subject: Re: Young programmers read me.
- Date: 20 Mar 1996 20:31:21 GMT
- Organization: The Wollongong Group
- Message-ID: <4ippuq$4pk@scoop.eco.twg.com>
- References: <4icpp9$7hr@barad-dur.nas.com> <4imqe4$cj3@ping1.ping.be>
- <Pine.SOL.3.91.960319174736.26863A-100000@solar.sky.net>
- <4iok3n$msv@guysmiley.blarg.net>
- NNTP-Posting-Host: vishnu.eco.twg.com
-
- In article <4iok3n$msv@guysmiley.blarg.net>, vanevery@blarg.net (Brandon J. Van Every) writes:
-
- >John Howard (jhoward@solar.sky.net) wrote:
- >: Using Ada 95 will save you a tremendous amount of time otherwise spent on
- >: debugging and maintenance hacks.
-
- >Other than evangelizing Ada in forums like this, and/or suggesting
- >that Ada showcase OS's be built, can you suggest some practical ways
- >to cause the software industry to eventually embrace Ada?
-
- Point out that 5/8 (or more) of the cost of software is in maintenance, and
- that anything that reduces maintenance costs, even if it increases development
- costs slightly, is a boon to profitability. Bottom-line arguments are hard to
- put asside...especially for the folks who tend to get to make the decisions
- (i.e. not the programers).
-
- Using Ada tends to require (so I'm told by those in the know) a bit more
- up-front planning and design than just hacking something together with C
- (though C++ should take at least as much extra planning to avoid disasters),
- but you end up spending considerably less time at the end of the project when
- the inevitable change requests, new features and endless debugging come up (you
- don't have to debug if you didn't put the bugs in in the first place ;^).
-
- It's also easier to add features to properly written software and you spend far
- less (time and money) on fixing bugs after adding the features. What software
- has never needed a new feature added later?
-
- Will using Ada suddenly turn a lousy hacker into a proficient software
- engineer? Of course not. You still have to know how to put together a good
- design, but with the language looking out after the more common coding
- blunders you can spend more time thinking about the global design and less
- about which type conversions are implicit and which have to be declared, and
- whether or not that variable is a static global or an automatic local, or
- whether your single character typo will make it through the compiler without
- a hitch and generate something other than what you wanted. (if you code in
- C, tell me you've never typed "=" when you meant "==" in an if statement's
- boolean...or tried tracking down the cause of a problem when you typed "/*"
- rather than "*/" to close a comment).
-
- Sure, it's less flamboyant and "macho" to just engineer good software, code
- it and have it work and be simple to maintain, but the old days of "it was
- hard to write, it should be hard to modify" and 18-24 hour "crunch" days at
- the end of the project when you have "just one more bug...or maybe two..."
- need to be over. Customers don't like having to use support lines to get
- problems fixed any more than companies like to pay to provide them.
-
- If you don't agree, check out any of the Corel newsgroups and see how thier
- customers feel about the seemingly endless bugs in their products. Sure, they
- fix them...eventually (I was up to CorelDRAW 5.0 rev F before things started
- working properly)...but how many hundreds of thousands of lost production hours
- are created by pointer bugs, memory leaks, unintended type conversions, array
- out of bounds errors, and other types of errors made simple by C/C++ and less
- easy to generate by other languages, such as Ada? Corel has said publicly that
- it isn't possible to write bug-free code in a comptitive marketplace using C or
- C++...it just takes too much time in those languages and they'd likely miss
- something anyway, so they don't bother and just let the customers locate those
- bugs that really bother them.
-
- Why do so many people use C and C++? Because everyone else seems to be doing
- it, so it's less risky in some minds, and because Unix vendors and Microsoft
- tend to provide support in the form of definition files, and libraries for
- those languages and not for others. Is this a good reason not to change? I
- don't think so, and if enough folks do change and it makes them more
- profitable, others will follow. If not, we'll stay where we are. That's life.
-
- Students should learn C/C++ because that's what will get them a job in the near
- future (just as FORTRAN and Pascal did when I was in school), but they should
- also learn more advanced and better-designed languages too, because that's
- probably what they'll be using in a few years. Maybe Ada, maybe not, but
- *someone* will start it and everyone else will either follow or die of
- inefficiency.
-
- -- Mike "the only constant is change" Bartman --
-
- ==============================================================================
- | I didn't really say all the things that I said. You probably didn't read |
- | what you thought you read. Statistics show that this whole thing is more |
- | than likely just a hideous misunderstanding. |
- ==============================================================================
- Poets go from bad to verse
- ==============================================================================
-
-